tracing-journald: prepare to release v0.3.0 #2085
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# 0.3.0 (April 21, 2022) This is a breaking release which changes the format in which span fields are output to `journald`. Previously, span field names were prefixed with the depth of the span in the current trace tree. However, these prefixes are unnecessary, as `journald` has built in support for duplicated field names. See PR [#1986] for details on this change. ## Changed - Removed span field prefixes ([#1986]) - Renamed `S{num}_NAME` fields to `SPAN_NAME ([#1986]) ### Fixed - Fixed broken links in documentation ([#2077]) Thanks to @wiktorsikora and @ben0x539 for contributing to this release! [#1986]: #1986 [#2077]: #2077
hawkw
force-pushed
the
eliza/journald-0.3
branch
from
e2f9376
to
5083e2d
Compare
Ralith
approved these changes
Apr 21, 2022
|
For anyone else looking back on this, the changes were in #1968 (the 6 and the 8 were transposed). |
Whoops, my bad --- thanks for catching that! I'll fix the changelog. |
kaffarell
pushed a commit
to kaffarell/tracing
that referenced
this pull request
May 22, 2024
# 0.3.0 (April 21, 2022) This is a breaking release which changes the format in which span fields are output to `journald`. Previously, span field names were prefixed with the depth of the span in the current trace tree. However, these prefixes are unnecessary, as `journald` has built in support for duplicated field names. See PR [tokio-rs#1986] for details on this change. ## Changed - Removed span field prefixes ([tokio-rs#1986]) - Renamed `S{num}_NAME` fields to `SPAN_NAME ([tokio-rs#1986]) ### Fixed - Fixed broken links in documentation ([tokio-rs#2077]) Thanks to @wiktorsikora and @ben0x539 for contributing to this release! [tokio-rs#1986]: tokio-rs#1986 [tokio-rs#2077]: tokio-rs#2077
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
0.3.0 (April 21, 2022)
This is a breaking release which changes the format in which span fields
are output to
journald. Previously, span field names were prefixedwith the depth of the span in the current trace tree. However, these
prefixes are unnecessary, as
journaldhas built in support forduplicated field names.
See PR #1986 for details on this change.
Changed
S{num}_NAMEfields toSPAN_NAME(#1986)Fixed
Thanks to @wiktorsikora and @ben0x539 for contributing to this release!